Credit Card Processors

Credit Card Processors define the account information, including login credentials, necessary to communicate with the Net1 payment gateway used by Deacom to process credit cards. Deacom does not have any special access/setup instructions for using the Net1 processor. Customers will need to make arrangements with these processor gateways independently.

Once the account(s) has been set up, the appropriate information and credentials can be entered into the Credit Card Processors account table. Users may opt to set up a test account during implementation of the feature. Once testing has been completed, users must remember to activate and configure the account for live transactions before accepting real orders. Once real orders are being received, credit cards may be used to process/pay for them.

System Navigation

Accounting > Maintenance > Credit Card Processors

Edit Credit Card Processor form

Opened via the "New" or "Modify" buttons on the Credit Card Processors form.

Field/Flag	Description
Processor	Pick list used to select the appropriate Credit Card Processor. Options are: 3 Delta - Utilizes 3 Delta's Payment WorkSuite payment gateway. (Note: Beginning in version 17.03, the 3 Delta Credit Card processor is no longer supported in Deacom as the 3 Delta company is no longer processing cards after 2023. To create a test account, customers will need to contact 3 Delta System directly. The Credit Card Processor must be defined on the General tab of the Bill-to Companies that will use the processor for credit card payments. Once 3 Delta Credit Card Processors have been created, the Credit Card Processor must be defined on the General tab of the Bill-to Companies that will use this processor for credit card payments. 3 Delta w/Card Vault - Utilizes 3 Delta's Payment WorkSuite payment gateway. Allows companies to store credit card data using 3 Delta's credit card tokenization and storage services. (Tokenization is the process of replacing sensitive data with unique identification symbols that retain all the essential information about the data without compromising its security.) (Note: Beginning in version 17.03, the 3 Delta Credit Card processor is no longer supported in Deacom as the 3 Delta company is no longer processing cards after 2023.) Card Pointe - Utilizes the CardConnect payment gateway. To create a test account, customers will need to contact CardConnect directly. This Overview of CardConnect provides useful information as well as the link to setup test credentials. Datacap - Utilizes the NetEPay payment gateway. Supports compliance for EMV cards, which are smart cards (also called chip cards or IC cards) that store their data on integrated circuits in addition to magnetic stripes (for backward compatibility). To create a test account, customers will need to contact DataCap directly. The default credit card processor that will be used in the system and the ability to download EMV parameters to pin pads is managed via File > Settings. The Sales Options contain a "Verbose EMV Logging" flag. When this flag is checked, Deacom will log all EMV requests and responses to a text file in (user profile)\AppData\Roaming\Deacom\. FullPayment - Utilizes the FullPay payment gateway. To create a test account. customers will need to work with FullPay directly. Note that the API key provided by FullPay will need to be inserted in the Credit Card Processor section in Deacom. Moneris - Utilizes the Merchant Resource Center payment gateway. To create a test account, customers will need to work with Moneris directly. If using the Moneris processor, the "Transact In Test Mode" flag, available on the Credit Card Processor form when selecting a "Processor" type of Moneris, can be checked to add an additional layer of security to ensure that actual payments are not processed. A valid two digit country code must be inserted in the "Country" field on the Company tab in System Options. Note: There is no separate "Transact in Test Mode" flag for the other Processor types. NET1 - Utilizes ECI's NET1 payment gateway. If using the NET1 processor, a valid account will be created upon saving the mandatory fields in the Edit Credit Card Processors form. This includes an account for when the "Transact in Test Mode" flag is checked. When saving a Sales Order or when accessing a Cash Receipt, a NET1 window will open separately to input payment information. If the window does not successfully open, you may need to check your browser's pop-up prevention settings. Notes: The user must be using HTTPS to successfully access eCommerce using NET1. Partial refunds using NET1 are not available at this time. Beginning in version 17.02.012, mmultiple NET1 accounts may be setup. This allows for multiple Net1 processors for different company databases or different Facilities. The location ID, associated with the Location field, will be the identifier to differentiate when specifying Net1 processors on Bill-To and Facility records. Further enhancements where made to this process in version 17.02.017. Multiple Net1 CC processors may be stored and used at the Bill-To Facility level. If a Net1 CC Processor is defined on a Facility, and that Facility is used with this Bill-To record to create an order via Net1, Net1 returns a specific ID number for the Facility/CCProcessor/Bill-To combination. The Deacom system will then check if there is a matching Bill-To Facility defined on Edit Bill-To Facility form with the existing Net CCProcessor defined. If a match is not found, Deacom will use this information to create a Bill-To Facility entry on that form and populate the Facility, CC Processor, and CC Proc Contact ID fields returned from Net1. All other fields will be left empty. This record can then be used for future Net1 transactions. Deacom will check for this record when sending information to Net1 and use the correct CC Proc Contact ID. When processing payments in NET1, (beginning in version 17.02.018) the card that is supplied no longer needs to have an address that matches the address on the Bill-To. NET1 EMV Uses EMV readers. (Igenico Lane 3000 series device currently supported) Ability to support NFC payments (Apple Pay, Google Pay, Tap) Accepts split payments that can contain non chip cards. Requires that a Register device be setup via System > Maintenance > Registers and a separate credit card processor entitled "Net1 EMV". Payflow - Utilizes PayPal's PayFlow Pro payment gateway. If using the PayFlow processor, the "Transact In Test Mode" flag, available on the Credit Card Processor form when selecting a "Processor" type of Payflow, can be checked to add an additional layer of security to ensure that actual payments are not processed. Note: There is no separate "Transact in Test Mode" flag for the other Processor types. Deacom also allows multiple PayPal merchant ID's/accounts to be established to provide companies greater flexibility. Payflow with Braintree- Linked to Payflow. Additional Information: Braintree Braintree is linked with Payflow, and requires an account with Payflow in addition to Braintree credentials.
Name	Displays the name of the account when making selections on records.
Partner	Indicates the ID provided by the authorized PayPal Reseller who registered the company for the Payflow SDK. If the account was purchased directly from PayPal, use PayPal. Only available if "Processor" is set to "Payflow".
Merchant/Merchant ID	Displays as "Merchant" when Processor is set to "Payflow" and as "Merchant ID" for all Processor types. Indicates the merchant login ID that was created when the company registered for the account.
Location	Indicates the location, generally company name, for the selected processor. Useful in situations where companies will have multiple processors. Only available if "Processor" is set to "3 Delta", "3 Delta w/Card Vault", and, beginning in version 17.02.012, Net1. (When using 3 Delta the location information is provided by 3 Delta)
Terminal Code	Only available if "Processor" is set to "3 Delta," "3 Delta w/Card Vault," or "Moneris."
Client Code	Only available if "Processor" is set to "3 Delta" or "3 Delta w/Card Vault."
User	Indicates the user for this account. If one or more additional users were set up on the account, this value is the ID of the user authorized to process transactions. If, however, additional users have not been set up on the account, this field can be left blank. Only available if "Processor" is set to "Payflow," "3Delta," "3Delta w/ Card Vault," or "Card Pointe."
Password	Stores the PayFlow password that was defined while registering for the account. Only available if "Processor" is set to "Payflow," "3Delta," "3Delta w/ Card Vault," or "Card Pointe."
API Key	Only available if "Processor" is set to "FullPayment". Indicates the required API key that is provided when creating an account for the FullPay payment gateway.
Host	Indicates the address to the server that the processor is running on. Only available if "Processor" is set to "Datacap" or "Card Pointe."
Host Port	Indicates the port that the processor is listening on. This port is 9000 by default for Datacap and 6443 for CardPointe. Only available if "Processor" is set to "Datacap" or "Card Pointe." Note: This field is no longer enabled for CardPointe processors beginning in version 16.07.118.
Active	If checked, this record is active. Only active records may be used in the system. If unchecked to make inactive, all Bill-To Companies with the selected CC Processor will have it removed from their respective records.
Default	If checked, the selected record is the default PayFlow account, which will be used when processing credit card transactions and payments unless the Facility or Bill-to Company on the transaction has a different PayFlow account specified. The Payflow credit card processor hierarchy, as of version 16.00.068, is: Bill-To Company CC processor, located in Sales > Customers > Modify Bill-To Company Facility CC processor (via the CC Processor field on the Facility Sales tab) System Default CC Processor (enabled via this flag) This field is only available if "Processor" is set to "Payflow".
Require Terminal ID	If checked, tells the Deacom system that the process requires the ID of the hardware to be sent back to the processor. Only available if "Processor" is set to "Datacap".
Transact In Test Mode	If checked, all transactions will flow through the test server for the selected credit card processor, and the credit card numbers used will not actually be charged. All other behavior and reports should be the same as a real transaction. Available for all credit card processors except DataCap and CardPointe. In addition to un-checking this flag, companies also need to ensure the PayPal account is not in test mode by activating the account. When checking this field, and using the FullPayment processor, the credit card expiration date will be exclusively set to "10/25" regardless of the expiration date specified in Deacom. This flag is unchecked by default. (beginning in version 17.02.019.0000) Note: Customers should not use test mode with Net1. They should test in production using test credit cards.